-
Notifications
You must be signed in to change notification settings - Fork 1
Introduce CCVProvider interface. #315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Code coverage report:
|
E2E Smoke Test Results
Full logs are available in the workflow artifacts. |
| // - Define a LOOPP client for this interface. | ||
| type CCVProvider interface { | ||
| Client() client.Client // verifier, executor | ||
| HeadTracker() heads.Tracker // verifier |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we replace this with the HeadTracker interface we use in the verifier?
| // - Create an adapter layer for legacyevm.Chain that implements this interface. | ||
| // - Define a LOOPP client for this interface. | ||
| type CCVProvider interface { | ||
| Client() client.Client // verifier, executor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know how this is gonna work for non-EVMs, the clients may have literally nothing in common.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the SourceReader interface should serve all of our chain reading purposes, if it doesn't then its not complete IMO
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Analogous to ChainAccessLayer in 1.6)
Placeholder for CCVProvider interface. Introduced now to clarify where chain agnostic abstractions will be implemented.